Skip to content

arxiv digest: author bylines + longer highlight summaries - #77

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/arxiv-papers-authors-longer-summaries
Jul 14, 2026
Merged

arxiv digest: author bylines + longer highlight summaries#77
Jammy2211 merged 1 commit into
mainfrom
feature/arxiv-papers-authors-longer-summaries

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Adds author names and longer summaries to the daily arXiv #papers Slack digest, per user request (today's post had only title + summary).

Change

Prompt-only edit to the Claude summariser step in .github/workflows/arxiv_papers.yml:

  • Author byline — each highlight now gets an italic byline line under the title listing the first up to 5 authors, then et al. if there are more.
  • Longer summaries — highlight summaries go from 2–3 → 4–5 sentences (method / data used + headline result + interest / caveats).
  • Updated the header comment to match.

The fetcher (arxiv_fetch.py) already includes authors in arxiv_papers.json, so no fetcher change was needed. The "THE REST" compact list and empty-day heartbeat are unchanged.

🤖 Generated with Claude Code

The #papers arXiv digest highlights showed only title + summary. Add an
author byline (first up to 5 authors, then "et al.") on its own line under
the title, and lengthen each highlight summary from 2-3 to 4-5 sentences
(method / data + headline result + interest / caveats).

Prompt-only change in the Claude summariser step; the fetcher already
supplies `authors` in arxiv_papers.json, so no fetcher change is needed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Jammy2211
Jammy2211 merged commit 46fe9f6 into main Jul 14, 2026
@Jammy2211
Jammy2211 deleted the feature/arxiv-papers-authors-longer-summaries branch July 14, 2026 07:16
Jammy2211 pushed a commit that referenced this pull request Jul 27, 2026
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Jammy2211 pushed a commit that referenced this pull request Jul 27, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Jammy2211 added a commit that referenced this pull request Aug 10, 2026
The Mind side of the compile-axis arc, from re-scope to completion records.
All four code PRs are already merged: PyAutoBrain#219 (cd79005),
autolens_profiling#104 (355d555), PyAutoBrain#220 (74d7b1b), PyAutoBrain#222
(a50efc3).

The 2026-07-14 prompt asked the Profiling Agent to measure compile time of the
release-validation heavy scripts so we could speed them up. Both halves of that
framing were spent. The speed-up shipped -- the #71/#74/#77 arc landed the
persistent compilation cache (117.0s -> 2.3s CPU; 5517.8s -> 937.1s A100) and
--xla_gpu_autotune_level=0 (17x on the pathological cold probe), and ruled out
source jit-boundaries by evidence. The release-scripts leg belongs to hygiene's
perf mode by both agents' documented boundaries, having been moved out of
profiling's staged future modes once already.

What survived is regression surveillance: both wins are SETTINGS, so a config
drift or an XLA_FLAGS clobber (the PyAutoNerves#127 failure that went
undetected for two months) puts the 70-minute worst case back with nothing
failing. Split into three sequential phases; the workspace-side
jax_compile_time_profiling.md was absorbed into phase 2, since the dashboard
and the agent reading it are two halves of one thing.

Contains the re-scoped parent prompt (original text preserved for provenance),
three completion records under complete/2026/08/, a regenerated index, and the
absorbed-prompt marker. active.md returns to just the two release drives.

The records preserve the traps, every one of which surfaced by running the
tools against real data rather than from the design:

- cache_dir is non-empty on COLD rows too -- the cold run populates the cache
  -- so warmness cannot be read from it or from the tag
- `hardware` alone pooled a laptop and a 32-core RAL node under one label; the
  first rendered dashboard put pins from both side by side
- pins auto-following the newest row would have baked a regression in
  permanently, reporting all-clear forever
- rows predating a pin are history, not drift
- export_probe.py / trace_profile.py share the results tree with a different
  schema, so their records are not malformed

Also records two corrections to earlier claims in this branch: the sweep grid
is 21 cells rather than 24, and the workspace test that looked red outside CI
was a missing matplotlib rather than a defect.

lifecycle.py check OK; 127 Mind tests pass; all three modes verified end to end
on merged main against the merged workspace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant